Voice action discoverability system

ABSTRACT

Methods, systems, and apparatus for receiving, by a voice action system, data specifying trigger terms that trigger an application to perform a voice action and a context that specifies a status of the application when the voice action can be triggered. The voice action system receives data defining a discoverability example for the voice action that comprises one or more of the trigger terms that trigger the application to perform the voice action when a status of the application satisfies the specified context. The voice action system receives a request for discoverability examples for the application from a user device having the application installed, and provides the data defining the discoverability examples to the user device in response to the request. The user device is configured to provide a notification of the one or more of the trigger terms when a status of the application satisfies the specified context.

TECHNICAL FIELD

This specification relates to voice actions, and one particularimplementation relates to configuring voice actions and educating usershow to use voice actions.

BACKGROUND

A task in an application can include one or more activities defined insoftware that a user interacts with to perform a certain job. Theactivity is a class that controls the life cycle of the execution of thetask, such the multiple activities exercised within the task can permitthe user to perform the job. In some implementations, a command can beassociated with an activity or an action related to an activity, suchthat a user submission of the command can trigger the activity oraction. A specific intent can be fired to trigger the starting of theactivity or performance of the action. Thus, to trigger the starting ofthe activity or performance of the action, a user must have knowledge ofthe command associated with the activity or action used to fire theintent corresponding to the activity or action.

SUMMARY

This specification describes a platform that allows an applicationdeveloper to deploy new voice actions for previously installed softwareapplications, and implement discoverability examples that inform usershow to use the deployed voice actions. In general, using the platform,the application developer can submit information defining the new voiceaction, where the information specifies the application, an action thatthe new voice action is directed to triggering, a trigger term fortriggering the action, and a context in which the trigger term should beeffective to trigger the action in the application. The applicationdeveloper can also submit information defining discoverability examplesfor the new voice action, such that a user of the application can bepresented with an appropriate discoverability example indicating how theuser can trigger the action.

The context submitted by the application developer can specify a userdevice status when the voice action should be effective to trigger theaction in the application. A device status can include, for example,which application(s) is operating in the foreground (i.e., currentlyactive in a user interface of the device) or in the background (i.e.,currently hidden from view in the user interface of the device), or caninclude specific information about applications, such as what activitiesthey are currently running, the status of running activities, and so on.

When the application developer submits information defining the newvoice action, the platform, designed as a service or tool, can validatethe information defining the new voice action to determine whether thenew voice action is compatible with the application, or to otherwisedetermine whether the new voice action can be implemented. If the newvoice action is valid, a new instance of a passive data structure calledan intent and having a specific format can be created for the voiceaction by inducting the information defining the new voice action. Theintent can specify some or all of the information defining the new voiceaction, such as the application, the trigger term, the activity oraction to be triggered in response to detecting the trigger term, andcontext that is necessary for the trigger term to trigger the activityor action. The voice action can then be deployed for the application,such that the voice action becomes an enabled voice action for theapplication without additional alterations being made to the applicationcode to support the voice action.

Once the voice action has been deployed, a user operating a user devicecan provide a speech input. The user device can submit contextinformation for the user device, and the context information and atranscription of the speech input can be used to identify an intent andto trigger the identified intent. When the intent is triggered, data forexecuting the activity or action is determined, and is transmitted tothe user device to execute the activity or action in response to thevoice input.

For example, an application developer of a media player application candefine a new voice action for skipping ahead in a song by apredetermined amount of time that uses the trigger term “skip ahead.”For example, the application developer can define a new voice action forskipping ahead by 30 seconds, 60 seconds, or by some other predeterminedamount of time in a song that the media player application is currentlyplaying. The application developer can specify a context when the “skipahead” voice action should be enabled. For example, the applicationdeveloper may specify that the “skip ahead” voice action should onlycause the media player application to skip ahead by the predeterminedamount of time in the song when the media player application is runningin the foreground and is in a mode that causes the media playerapplication to operate as an audio player. After the voice action hasbeen deployed by the application developer, a user having the mediaplayer application previously installed on their user device mightsubmit the voice input “skip ahead.” The user device can submit contextinformation indicating a status of the user device or of applicationsinstalled on the user device, such as context information indicatingthat the media player application is running in the foreground and is inaudio player mode. In response to receiving the voice input “skip ahead”and the information specifying the context, data can be transmitted tothe user device that causes the media player application to skip aheadby the predetermined amount of time in a song that the media playerapplication is currently playing. In contrast, if the voice input isdetermined to say “skip ahead” but the context information indicatesthat a social networking application is running in the foreground of theuser device instead of the media player application, then the “skipahead” voice input may not have any effect, or may cause a differentoperation to be performed at the user device.

Because application developers may deploy any number of new voiceactions for a previously installed application, and since those newvoice actions may be available to users in a number of differentcontexts, the platform allows application developers to definediscoverability examples that can presented to users to inform the usersof available voice actions for a specific context. When submittinginformation defining a new voice action, an application developer mayinclude information that defines one or more discoverability examplesfor the new voice action. Discoverability examples may includenotifications, such as textual, image, video, or audio notifications,that can be presented to a user of the software application to inform auser that the voice action is available in the present context and howthe user can trigger the new voice action.

The information submitted by the application developer defining thediscoverability example, can be received by the platform and used togenerate data that defines the discoverability example. In someimplementations, the generated data can then be provided to user deviceshaving the application installed, and stored at the respective userdevices. Storing the generated data at a user device can enable the userdevice to provide discoverability examples off-line. Thus, if a user ofa client device requests discoverability examples in a given context,the user device may be capable of determining the context and selectingdiscoverability examples stored at the device to provide based on thecontext, where the selected discoverability examples correspond to voiceactions that are capable of being triggered in the current context.

For example, when defining the “skip ahead” voice action, theapplication developer may also define a discoverability example for the“skip ahead” voice action that includes the textual notification, “TrySaying ‘Skip Ahead’.” The platform may generate data defining thediscoverability example and may transmit the generated data to one ormore user devices having the media player application installed. Thegenerated data may be stored at the one or more user devices.Subsequently a user of a user device having the media player installedmay request discoverability examples for a current context, for example,by providing a voice input to the user device that includes “What voicecommands can I say?” The user device may interpret this voice input as arequest for discoverability examples, and may determine a context forthe user device and the media player application. Based on determiningthat the context matches a context for the discoverability exampleassociated with the “skip ahead” voice action, the user device mayaccess information for the discoverability example, and provide atextual notification at the user device that includes the text of thediscoverability example, “Try Saying ‘Skip Ahead.” The user may rely onthis discoverability example in determining voice actions available tothe user device given the current context of the user device or themedia player application.

Innovative aspects of the subject matter described in this specificationmay be embodied in methods, systems, and non-transitorycomputer-readable storage devices performing operations includingreceiving, by a voice action system, data specifying trigger terms thattrigger a software application to perform a new voice action and acontext that specifies a status of the software application when the newvoice action can be triggered, receiving, by the voice action system,data defining a discoverability example for the new voice action,wherein the data defining the discoverability example comprises one ormore of the trigger terms that trigger the software application toperform the new voice action when a status of the software applicationsatisfies the specified context, receiving, by the voice action systemfrom a user device having the software application installed, a requestfor discoverability examples for the software application, andproviding, by the voice action system, the data defining thediscoverability example to the user device in response to the request,wherein the user device is configured, based at least on the datadefining the discoverability example, to provide a notification of theone or more of the trigger terms when a status of the softwareapplication satisfies the specified context.

These and other embodiments may each optionally include one or more ofthe following features. In various examples, these and other embodimentsmay each optionally include features comprising: receiving, by the voiceaction system, data corresponding to content that is presentable at auser device as a notification of the one or more of the trigger terms,and providing, by the voice action system, the data corresponding to thecontent to the user device in response to the request, wherein the userdevice is configured, based at least on the data corresponding to thecontent to present the content as a notification of the one or more ofthe trigger terms when a status of the software application satisfiesthe specified context. In various examples, these and other embodimentsmay each optionally include features comprising: generating, by thevoice action system, data defining one or more unique candidatediscoverability examples for the new voice action, wherein data definingeach of the one or more unique candidate discoverability examplescomprises one or more of the trigger terms, receiving, by the voiceaction system, data indicating a selection of a particular candidatediscoverability example from among the one or more unique candidatediscoverability examples, and providing, by the voice action system,data defining the particular candidate discoverability example to theuser device in response to the request, wherein the user device isconfigured, based at least on the data defining the particular candidatediscoverability example, to provide a notification of the one or more ofthe trigger terms that corresponds to the particular candidatediscoverability example when a status of the software applicationsatisfies the specified context.

In various examples, these and other embodiments may each optionallyinclude features comprising: receiving, by the voice action system fromthe user device having the software application installed, dataindicating a status of the software application, determining, by thevoice action system and based on the data indicating the status of thesoftware application, that the status of the software applicationsatisfies the specified context; and providing, by the voice actionsystem, the data defining the discoverability example to the user devicein response to determining that the status of the software applicationsatisfies the specified context, wherein the user device is configured,based at least on the data defining the discoverability example, toreceive the discoverability example and to provide a notification of theone or more of the trigger terms in response to receiving thediscoverability example.

In various examples, the specified context indicates that the softwareapplication is performing a specific activity; the specified contextindicates that a specific activity that the software application isperforming is in a particular activity state; the specified contextindicates that the software application is operating in the foregroundof a user device having the software application installed; thespecified context indicates that the software application is operatingin the background of a user device having the software applicationinstalled.

In various examples, these and other embodiments may each optionallyinclude features comprising: receiving, by the voice action system, dataspecifying (i) trigger terms that trigger the software application toperform a second new voice action and (ii) the specified context,receiving, by the voice action system, data defining a seconddiscoverability example for the second new voice action, wherein thedata defining the second discoverability example comprises one or moreof the trigger terms that trigger the software application to performthe second new voice action when a status of the software applicationsatisfies the specified context, and providing, by the voice actionsystem, the data defining the second discoverability example to the userdevice in response to the request, wherein the user device isconfigured, based at least on the data defining the seconddiscoverability example, to provide a notification of the one or more ofthe trigger terms that trigger the software application to perform thenew voice action and of the one or more of the trigger terms thattrigger the software application to perform the second new voice actionwhen a status of the software application satisfies the specifiedcontext.

In various examples, a status of the software application is determinedin response to detecting a user input at the user device that requests anotification of trigger terms that trigger the software application toperform voice actions; a status of the software application isdetermined in response to determining that a status of the softwareapplication has changed; a status of the software application isdetermined in response to determining that the software application hasbeen launched at the user device; the notification of the one or more ofthe trigger terms is one of a textual notification, an imagenotification, a video notification, or an audio notification. In variousexamples, these and other embodiments may each optionally includefeatures comprising: storing, at the voice action system, the datadefining the discoverability example at a database that includes datadefining one or more other discoverability examples, wherein at leastone of the one or more other discoverability examples is adiscoverability example for a different voice action.

In various examples, the user device is configured to: determine that astatus of the software application satisfies a context specified foreach of two or more different voice actions, identify discoverabilityexamples that are defined for the two or more different voice actions,wherein each of the discoverability examples comprises one or moretrigger terms that trigger the software application to perform one ofthe two or more different voice actions, select a subset of thediscoverability examples, and provide a notification of the one or moretrigger terms of each of the discoverability examples included in thesubset. In various examples, selecting the subset of the discoverabilityexamples comprises: ranking the discoverability examples that aredefined for the two or more different voice actions, and selecting thesubset of the discoverability examples based at least on the ranking. Invarious examples, selecting the subset of the discoverability examplescomprises: determining a relevance of each of the two or more differentvoice actions to the context specified for each of the two or moredifferent voice actions, and selecting the subset of the discoverabilityexamples based at least on the determined relevance of each of the twoor more different voice actions to the context specified for each of thetwo or more different voice actions. In various examples, selecting thesubset of the discoverability examples comprises: accessing informationindicating past user activity at the user device when the status of thesoftware application satisfies the context specified for each of the twoor more different voice actions, and selecting the subset of thediscoverability examples based at least on the accessed informationindicating the past user activity at the user device when the status ofthe software application satisfies the context specified for each of thetwo or more different voice actions.

The details of one or more embodiments of the subject matter describedin this specification are set forth in the accompanying drawings and thedescription below. Other potential features, aspects, and advantages ofthe subject matter will become apparent from the description, thedrawings, and the claims.

BRIEF DESCRIPTION OF THE DRAWINGS

FIGS. 1A, 1B, and 1C depicts an example system for a voice actiondevelopment system and service.

FIG. 2 depicts an example system for generating discoverability examplesfor voice actions using a voice action development system and service.

FIG. 3 depicts an example system for providing discoverability examplesfor voice actions.

FIG. 4 is a flowchart of an example process associated with a voiceaction development system and service.

Like reference symbols in the various drawings indicate like elements.

DETAILED DESCRIPTION

FIG. 1A illustrates an example of a voice action system 100. The voiceaction system 100 provides a platform and service whereby an applicationdeveloper can establish new voice actions for an application that haspreviously been installed on other users' devices. Thereafter, users ofthe application having the application installed on their devices canuse voice commands in order to cause the application to perform aspecific operation as specified by the new voice action. The voiceaction system 100 may also provide a platform and service, discussed infurther detail with respect to FIGS. 1B and 1C, whereby the applicationdeveloper can establish discoverability examples for voice actions. Thediscoverability examples can be provided to users to inform them ofvoice actions that are available and how those voice actions can betriggered.

The voice action system 100 receives from terminals 102 a-102 n datadefining new voice actions submitted by application developers 101 a-101n, wherein the new voice actions are for one or more differentapplications. The voice action system 100 can determine whether each newvoice action is a valid voice action. Each new voice action that isdetermined to be valid can be inducted to generate an intentcorresponding to the new voice action, and the intent corresponding tothe new voice action can be stored at an application voice actiondatabase 110 of the voice action system 100.

For example, the voice action system 100 may have a validation enginethat receives and validates the data defining the new voice action.Validating the data may include determining that the formatting of thedata defining the voice action complies with requirements, determiningthat the new voice action is compatible with the specified application,or otherwise determining that a voice action can be established based onthe data received from the application developer 101 a-101 n. Anindication engine of the voice action system 100 can receive thevalidated data defining the new voice action, and can induct the data togenerate the intent corresponding to the new voice action. The intentcan then be stored in the application voice action database 110.

The application voice action database 110 can store voice actions thatpertain to activities or actions that can be performed within numerousdifferent software applications. The voice actions included in theapplication voice action database 110 may include built-in voice actionsthat were submitted by application developers 101 a-101 n when theapplication was built, as well as voice actions that were submitted byapplication developers 101 a-101 n after the application was built foroperations supported by the application.

The voice actions can also include application-specific voice actionsthat are supported by default by the operating system. Thesepre-supported voice actions may be voice actions that are capable ofbeing implemented in applications without having to be submitted to thevoice action system 100 by an application developer 101 a-101 n. Forexample, the voice action “exit application” to exit a task or activityrunning in the foreground may be automatically available for anyapplication, and may be included in the application voice actiondatabase 110 for each application, without an application developer 101a-101 n having to submit information to the voice action system 100 todefine the “exit application” voice action.

In addition to the application voice action database 110, the voiceaction system 100 can include an operating system (OS) voice actiondatabase 120 that stores voice actions that are not associated with anyparticular application or context. For example, a “lock phone” voiceaction that causes a device to enter a locked state may be a voiceaction that is specified in the OS voice action database 120 as a voiceaction that is not associated with a particular application, or that isuniversally accessible, i.e., regardless of a device's status when the“lock device” voice action is detected. Generally, the voice actionsstored in the OS voice action database 120 are voice actions that arenot generated based on application developers 101 a-101 n defining thevoice actions, since the voice actions stored at the OS voice actiondatabase 120 are generic to a user device operating environment and notany particular application generated by third party applicationdevelopers 101 a-101 n.

The voice action system 100 enables a user 105 having a user device 104to provide spoken voice input to their user device 104 to cause actionsto be performed by the user device 104 or applications operating ontheir user device 104. For example the user 105 having the user device104 has a media player application running on their user device 104 andprovides the spoken input “skip ahead” while the media playerapplication is running in the foreground of the user device 104 and isoperating the media player application in an audio player mode.

Audio data corresponding to the spoken input and context informationspecifying a status of the user device 104, including the status ofapplications running on the user device 104, is transmitted to the voiceaction system 100. Specifically, for the example shown in FIG. 1A, theaudio data corresponding to the voice input “skip ahead” is received bya speech recognition engine 130 of the voice action system 100, and thecontext information indicating the status of the user device 104 isreceived by a context analysis engine 140 of the voice action system100. The context information may indicate that the media playerapplication is running in the foreground of the user device 104, thatthe media player application is currently in an audio player mode, andmay indicate other information about the status of the user device 104and applications installed on the user device 104.

The speech recognition engine 130 receives the audio data correspondingto the voice input, generates a transcription of the voice input, andprovides the transcription of the voice input to the voice actionselector 150. The context analysis engine 140 receives the contextinformation from the user device 104 and processes the contextinformation to determine relevant context information. For example, thecontext analysis engine 140 may analyze the context information toidentify applications that are installed on the user device 104, andmetadata associated with each of those applications may specifyavailable voice actions for the application and context information thatis relevant to determining which of the voice actions might be enabledfor a given device status. In some instances, based on the analysis, thecontext analysis engine 140 may determine that additional contextinformation is required to identify which voice actions should beenabled for a particular status of the user device 104, and so thecontext analysis engine 140 may request additional context informationfrom the user device 104. The context analysis engine 140 forwards theprocessed context information to the voice action selector 150.

For example, as shown in FIG. 1A, the speech recognition engine 130 mayreceive the audio data corresponding to the voice input “skip ahead” andmay obtain a transcription of the voice input. The context analysisengine 140 receives context information from the user device 104 thatspecifies that the media player application is running in theforeground, that the media player application is operating in an audioplayer mode, and that specifies other information about the user device104. For instance, the context information may also indicate that asocial network application is operating in the background of the userdevice 104 and that the battery life of the user device 104 is currently50%. The context analysis engine 150 may receive information indicatingthat the user device 104 has both the media player and social networkapplications installed and may determine that neither the media playerapplication nor the social network application enables voice actionsbased on context information that indicates a device battery life.Therefore, the context analysis engine 140 may filter the contextinformation to indicate only that the media player application isoperating in the foreground of the user device 104, that the mediaplayer application is in an audio player mode, and that the socialnetwork application is operating in the background of the user device104. The filtered context information and the transcription of the voiceinput “skip ahead” may then be provided to the voice action selector150.

The voice action selector 150 receives the transcription of the spokeninput from the speech recognition engine 130 and a context from thecontext analysis engine 140 that includes processed context information.The voice action selector 150 uses the transcription and the context toidentify a particular intent associated with a particular voice actionto trigger at the user device 104. For example, the voice actionselector 150 can access the application voice action database 110 andthe OS voice action database 120 to identify a set of candidate voiceactions that are enabled for the present context of the user device 104.Identifying the set of candidate voice actions can include identifying aset of intents stored at the application voice action database 110 orthe OS voice action database 120 that specify contexts matching thecontext received by the voice action selector 150.

Having identified the set of candidate voice actions that are enabledfor the presented context, the voice action selector 150 can compare thetranscription of the voice input to one or more trigger phrasesassociated with each of the enabled voice actions. In general, a triggerphrase can include one or more trigger terms, and operates as anidentifier for a voice action, such that detection of the one or moreterms of a particular trigger phrase results in identification andtriggering of the voice action corresponding to the particular triggerphrase. For instance, the voice action selector 150 can compare thetranscription to respective trigger phrases associated with the intentsof the enabled voice actions. The voice action selector 150 identifies aparticular intent for a particular voice action based on determiningthat the transcription matches a trigger term specified by the intentassociated with the particular voice action.

For example, the voice action selector 150 can receive the transcriptionof the voice input “skip ahead” and the context for the user device 104,and can use the received context to identify candidate voice actions toinitiate at the user device 104, i.e., voice actions that can beinitiated at the user device 104 based on the current status of the userdevice 104. After determining the set of candidate voice actions for thecontext of the user device 104, the voice action selector 150 comparesthe transcription of the voice input “skip ahead” to trigger phrasesspecified by the intents of the candidate voice actions. The voiceaction selector 150 can determine that the transcription “skip ahead”matches the trigger phrase specified by the intent of the “skip ahead”voice action for the media player application.

The “skip ahead” voice action may be a voice action for causing themedia player application to skip ahead by a predetermined amount of timein a song that the media player application is currently playing. Forexample, the “skip ahead” voice action may cause the media playerapplication to fast forward by a predetermined amount of time, such as30 seconds, 60 seconds, or other amount of time specified, for example,by an application developer 101 a-101 n or user 105. Thus, if the mediaplayer application is playing a song and is 1 minute and 15 seconds intothe song when it receives the “skip ahead” voice action, the mediaplayer application may skip ahead in the song to a point 1 minute and 45seconds into the song. In some examples, if the amount of time remainingin the song when the “skip ahead” voice action is received is less thanthe predetermined amount of time, the media player application may causethe media player application to skip ahead to a next song.

A transcription is identified as matching a trigger phrase based ondetermining that at least a portion of the transcription matches one ormore terms of the trigger phrase. For example, a match between atranscription and a trigger phrase may be identified based on each ofthe terms of the transcription matching each of the terms of the triggerphrase. In some implementations, a match may be identified based ondetermining that less than all of the terms of the transcription matchterms of the trigger phrase. For example, a transcription may match atrigger phrase even if some of the terms of the trigger phrase areabsent from the transcription, if the transcription includes terms inaddition to those of the trigger phrase, or if one or more terms of thetranscription are different from terms of the trigger phrase. Thus, eachof the transcriptions “new email,” “send new email,” or “open up newemail” may be identified as matching the trigger phrase “open newemail,” despite each of the transcriptions failing to precisely matchthe trigger phrase. In some instances, a transcription may be identifiedas matching a trigger phrase if the transcription includes some or allof the terms of the trigger phrase in a different order than the orderspecified by the trigger phrase. For example, the transcription “lockphone” may be identified as matching a “phone lock” trigger phrase. Insome instances, a transcription may be identified as matching a triggerphrase based on determining that the transcription includes one or moresynonyms or alternate terms for terms of the trigger phrase. Thus, thetranscriptions “draft new email” or “open new email” may be identifiedas matching the trigger phrase “write new email” based on “draft” beinga synonym of “write,” and “open” being an identified alternate term for“write.”

Having identified the particular voice action, the voice action selector150 provides action trigger data to the user device 104 that causes theactivity or action associated with the particular voice action to beinitiated. To do so, the voice action selector 150 can obtaininformation for controlling the user device 104 to perform the action oractivity associated with the selected voice action. In some instances,controlling the user device 104 to perform the action or activityassociated with the selected voice action can include firing an intentof the selected voice action. Firing the intent of the selected voiceaction may cause information for initiating the activity or actionassociated with the selected voice action to be provided to the userdevice 104.

For example, the intent for the selected voice action can include datathat causes actions or activities associated with the voice action to beperformed by the application associated with the voice action. Theselected intent can be transmitted to the user device 104, such thatreceipt of the intent by the user device 104 can act as a request or cantrigger performance of the actions or activities associated with thevoice action. Alternatively, the voice action selector 150 can determineother data to operate as action trigger data that causes the selectedvoice action to be performed at the user device 104, and can transmitthe information to the user device 104. For example, an intent may onlyidentify the actions or activities to be performed by the user device104 to perform the voice action, and the voice action selector 150 candetermine action trigger data that can control the application on theuser device 104 to perform the actions or activities associated with thevoice action. The determined action trigger data can be transmitted tothe user device 104 such that the action trigger data causes the actionsor activities associated with the voice action to be performed.

For instance, after selecting the “skip ahead” voice action from amongthe set of candidate voice actions, the voice action selector 150transmits the intent for the “skip ahead” voice action to the userdevice 104, or obtains other information for controlling the mediaplayer application running on the user device 104 to skip ahead by apredetermined amount of time in a song that the media player applicationis currently playing. The voice action selector 150 transmits the datafor controlling the media player application to skip ahead by thepredetermined amount of time in the song to the user device 104, whichin turn initiates a process for the media player application running onthe user device 104 to skip ahead by the predetermined amount of time inthe song, for example, to skip ahead by the predetermined amount of timein the song “Fame” by David Bowie.

Briefly, as discussed, the system of FIG. 1A includes one or moreterminals 102 a-102 n corresponding to one or more applicationdevelopers 101 a-101 n. The terminals 102 a-102 n can each be incommunication with the voice action system 100, for example, over one ormore wired or wireless networks. Each of the terminals 102 a-102 n canbe a mobile device, such as a cellular phone, smartphone, tabletcomputer, laptop computer, personal digital assistant (PDA), netbookcomputer, or other mobile computing device, or may be any stationarycomputing device, such as a desktop computer or other stationarycomputer. A user device 104 associated with a user 105 can also be incommunication with the voice action system 100 over one or more wired orwireless networks, where the user device 104 may also be a mobile orstationary computing device, such as a cellular phone, smartphone,tablet computer, netbook, personal digital assistant, laptop computer,desktop computer, or other computing device.

The example voice action system 100 shown in FIG. 1A includes anapplication voice action database 110, operating system (OS) voiceaction database 120, speech recognition engine 130, context analysisengine 140, and voice action selector 150. Each of the components of thevoice action system 100, including the application voice action database110, OS voice action database 120, speech recognition engine 130,context analysis engine 140, and voice action selector 150, may be incommunication with one or more other components of the voice actionsystem 100 over one or more wired or wireless data pathways that enablethat exchange of electronic communications. In some implementations, oneor more of the components of the voice action system 100 may be combinedsuch that their functions are performed by a single component, or may berepresented by two or more components such that their functions aredispersed across the two or more components. The components of the voiceaction system 100 may be implemented on a single computing device, suchas a single server system, or may be implemented on multiple computingdevices that are in communication over one or more wired or wirelessdata pathways that enable the exchange of electronic communicationsbetween the components.

FIG. 1B depicts a voice action system 100 that enables applicationdevelopers to establish discoverability examples for voice actions, andto provide appropriate discoverability examples to users.Discoverability examples submitted by an application developer maypertain to a new voice action established by the application developerfor a particular application, and may be presented at user deviceshaving the application installed to inform users how to trigger the newvoice action.

As shown in FIG. 1B, the voice action system 100 receives data fromterminals 102 a-102 n that specifies discoverability examples submittedby application developers 101 a-101 n. Each discoverability examplesubmitted to the voice action system 100 by an application developer 101a-101 n may pertain to a new voice action submitted by the applicationdeveloper 101 a-101 n for a particular software application.Discoverability examples submitted by application developers can bestored at a voice action discoverability example database 170 of thevoice action system 100.

For example, in some implementations, an application developer 101 a-101n may submit information to the voice action system 100 to define a newvoice action, as described with respect to FIG. 1A. In addition to theinformation defining the new voice action, the application developer 101a-101 n may submit information specifying one or more discoverabilityexamples that can inform a user of the software application how totrigger the new voice action. In some implementations, informationdefining a discoverability example for a new voice action can specifythe new voice action to which the discoverability example relates, mayspecify a context when the new voice action is available to users, mayspecify one or more trigger terms used to trigger the new voice action,or can include other information. In some implementations, theinformation specifying the discoverability example submitted to thevoice action system 100 by an application developer 101 a-101 n mayinclude the content of the discoverability example. For instance, theinformation transmitted to the voice action system 100 may include atextual notification or message, an image, a video, audio data, or othercontent that may be provided to users to inform a user how to trigger avoice action. The application developer 101 a-101 n may provideinformation defining multiple discoverability examples for the samevoice action, where different discoverability examples may be intendedfor presentation to different users, different types of user devices, orunder different circumstances.

As an example, an application developer 101 a-101 n developing the “skipahead” voice action for the media player application may submitinformation using a terminal 102 a-102 n that defines a discoverabilityexample for the “skip ahead” voice action. To define the discoverabilityexample for the “skip ahead” voice action, the application developer 101a-101 n may submit information that specifies one or more trigger termsused to trigger the “skip ahead” voice action, as well as informationthat specifies a context when the “skip ahead” voice action is capableof being triggered by a user. For instance, the submitted informationdefining the discoverability example may specify the trigger term “skipahead” as well as a context specifying that the voice action can beperformed when the media player application is operating in theforeground of a user device and is operating in an audio player mode.Additional or different information may also be submitted by theapplication developer 101 a-101 n to establish the discoverabilityexample. For instance, the application developer 101 a-101 n may submitinformation specifying the content of the discoverability example, suchas a message “Try Saying ‘Skip Ahead” that is to be presented to users.In other examples, an application developer 101 a-101 n may only need toprovide information specifying the new voice action for adiscoverability example for that voice action to be created by the voiceaction system 100. In some implementations, the application developer101 a-101 n may submit information defining multiple discoverabilityexamples for the “skip ahead” voice action. For example, the applicationdeveloper 101 a-101 n may submit information for a textualdiscoverability example for the “skip ahead” voice action, such as themessage “Try Saying ‘Skip Ahead,” as well as information for an audiodiscoverability example for the “skip ahead” voice action, such as arecording of a voice saying “Try Saying ‘Skip Ahead.”

In other implementations, the voice action system 100 may suggestdiscoverability examples to an application developer 101 a-101 n, suchthat the application developer 101 a-101 n need only select from amongthe suggested discoverability examples. For example, when an applicationdeveloper 101 a-101 n establishes a new voice action for an application,the voice action system 100 may be configured to generate one or morecandidate discoverability examples for the new voice action. The voiceaction system 100 provides information to the terminal 102 a-102 n ofthe application developer 101 a-101 n that enables the applicationdeveloper 101 a-101 n to select one or more discoverability examples toestablish for the new voice action. Data indicating the selections ofthe application developer 101 a-101 n may then be provided to the voiceaction system 100 by the terminal 102 a-102 n.

For example, when the application developer 101 a-101 n submitsinformation defining the “skip ahead” voice action as described withrespect to FIG. 1A, the voice action system 100 may generate one or morecandidate discoverability examples for the “skip ahead” voice action.The candidate discoverability examples may include, for example, thetextual message, “Try Saying ‘Skip Ahead,” the textual message, “Say‘Skip Ahead’ to Fast Forward 30 Seconds,” and a recording of a voicesaying “Try Saying ‘Skip Ahead.” The voice action system 100 may providethe candidate discoverability examples to a terminal 102 a-102 n of theapplication developer 101 a-101 n, and the application developer 101a-101 n may provide input to the terminal 102 a-102 n to select one ormore of the candidate discoverability examples. Data indicating theselections may be provided to the voice action system 100.

The voice action system 100 can receive the information specifying orselecting a discoverability example from the terminal 102 a-102 n of theapplication developer 101 a-101 n, and can generate data for thediscoverability example based on the received information. For example,the voice action system 100 may receive the information specifying thediscoverability example, and may induct the received data to generate adiscoverability example in a particular data type or format. In someimplementations where the voice action system 100 suggestsdiscoverability examples to application developers 101 a-101 n forselection, the voice action system may generate the discoverabilityexample, in the particular data type or format, before providing thesuggestions to the application developers 101 a-101 n. In such animplementation, upon receiving a user selection of a particularsuggested discoverability example, the voice action system 100 may beable to discard non-selected discoverability examples that the voiceaction system 100 generated, and may retain the selected discoverabilityexample for storage. Alternatively, the voice action system 100 mayprovide discoverability examples to application developers 101 a-101 nwithout generating the discoverability examples corresponding to thesuggest discoverability examples. Thus, the suggestions provided to theapplication developers 101 a-101 n may be representations of potentialdiscoverability examples. Upon receiving selection of a particularsuggested discoverability example, the voice action system 100 may thengenerate the discoverability example in the particular data type orformat.

Inducting information specifying a discoverability example generates adiscoverability example in a particular data type or format that may benecessary to presentation of the discoverability example at a userdevice, in a similar way that induction of the information defining anew voice action results in the generation of an intent for triggeringthe new voice action. For example, when an application developer 101a-101 n may submit information specifying only a trigger term used totrigger a new voice action and a context when the new voice action canbe triggered, the voice action system 100 may induct the information togenerate an item of a particular data type or format that specifiesinformation necessary for presentation of the discoverability example,such as the generation and formatting of a textual message to bepresented to a user, information indicating devices that are compatiblewith the particular discoverability example, or other informationrequired for presentation of the discoverability example at a userdevice.

The inducted discoverability example may be stored at the voice actiondiscoverability example database 170. For example, the voice actiondiscoverability example database 170 may include discoverabilityexamples pertaining to one or more different voice actions that can beperformed with respect to one or more different applications, operatingsystems, or devices, and the inducted discoverability example may bestored at the voice action discoverability example database 170. Thevoice action discoverability example database 170 may be included in thevoice action system 100, or may be accessible by the voice action system100 over one or more wired or wireless data pathways.

As shown in FIG. 1B, the voice action system 100 may also be capable ofprocessing a request for discoverability examples received from a userdevice 104, and of responding to the request by providing information tothe user device 104 that causes one or more discoverability examples tobe presented to the user 105. For example, after the discoverabilityexample for a new voice action has been stored at the voice actiondiscoverability example database 170, the voice action system 100 maydetect a request for discoverability examples received from the userdevice 104, and in response may identify discoverability examples toprovide to the user device 104.

As shown in FIG. 1B, in one example the user 105 may requestdiscoverability examples by providing the voice input “What voicecommands can I say?” to the user device 104. The user device 104 mayhave a connection to the voice action system 100 over one or more wiredor wireless data pathways, and so may transmit audio data correspondingto the voice input to the voice action system 100 where it is receivedby the speech recognition engine 130. The speech recognition engine 130may generate a transcription of the voice input based on the receivedaudio data. For example, upon receiving the audio data corresponding tothe voice input of the user 105, the speech recognition engine 130 maygenerate the transcription “What voice commands can I say?” and mayprovide the transcription to a discoverability example selector 160 ofthe voice action system 100.

Requests for discoverability examples can be provided to the voiceaction system 100 in other ways as well. For example, a user device 104may request discoverability examples from the voice action system 100 inresponse to a user providing an input requesting help or requestingdiscoverability examples, for example, by pressing a particular key orsymbol at the user device 104. The user device 104 may also requestdiscoverability examples from the voice action system 100 withoutrequiring an explicit user input. For example, the user device 104 maydetermine that a new application has been launched or reopened at theuser device 104 (e.g., brought to the foreground of the user device104), or that a status of an application or of the user device 104 haschanged, or that content displayed at the user device has changed, andin response to the determination may request discoverability examplesfrom the voice action system 100.

To request discoverability examples, for example, in response to thevoice input of the user 105, the user device 104 may also determine acontext of the user device 104 and applications operating on the userdevice 104. The user device 104 may transmit contextual information tothe voice action system 100, where it may be received by the contextanalysis engine 140. The context analysis engine 140 may process thereceived context information to determine a context that is relevant toidentifying discoverability examples.

For example, as discussed with respect to FIG. 1A, the context analysisengine 140 may receive a variety of context information from the userdevice 104, and may determine a subset of the context information thatis pertinent to identifying discoverability examples that should bepresented to the user 105 of the user device 104. For instance, thecontext analysis engine 140 may receive contextual information from theuser device 104 indicating that the media player application isoperating in the foreground of the user device 104, that the mediaplayer application is operating in an audio player mode, and that thebattery life of the user device 104 is 50%. The context analysis engine140 may determine that the battery life information is not relevant todetermining discoverability examples to present to the user 105, andtherefore may provide only the context information indicating that themedia player application is operating in the foreground of the userdevice 140 and is operating in an audio player mode to thediscoverability example selector 160.

The discoverability example selector 160 may receive the transcriptionof the voice input of the user 104 from the speech recognition engine130 and the relevant context from the context analysis engine 140, andbased on the received information may identify one or morediscoverability examples to provide to the user device 104 for output tothe user 105. For example, the discoverability example selector 160 maydetermine, based on the transcription, that the voice input of the user105 was a request for discoverability.

Based on determining that the voice input was a request fordiscoverability examples, the discoverability example selector 160 mayaccess the voice action discoverability example database 170 to identifydiscoverability examples associated with contexts that satisfy thecontext received from the context analysis engine 140. For example, thediscoverability example selector 160 may receive the context informationindicating that the media player application is operating in theforeground of the user device 104 and that the media player applicationis operating in an audio player mode, and so may identifydiscoverability examples stored at the voice action discoverabilityexample database 170 that also specify a context that includes the mediaplayer application operating in the foreground of a device and being inan audio player mode. To identify the discoverability examples, thediscoverability example selector 160 may compare the context receivedfrom the context analysis engine 140 to each of the discoverabilityexamples included in the voice action discoverability example database170, or may compare the received context to a subset of thediscoverability examples stored at the voice action discoverabilityexample database 170. Based on the comparison, the discoverabilityexample selector 160 may identify one or more discoverability examplesto provide to the user device 104 for presentation to the user 105.

In the example shown in FIG. 1B, the discoverability example selector160 may determine that the context specified by the discoverabilityexample established by the application developer 101 a-101 n for the“skip ahead” voice action matches the context received from the contextanalysis engine 140. In response to this determination, thediscoverability example selector 160 may transmit information to theuser device 104 that causes the discoverability example for the “skipahead” voice action to be output. For instance, the discoverabilityexample selector 160 may transmit the inducted discoverability examplefor the “skip ahead” voice action, in the particular data type orformat, to the user device 104, and upon receiving the inductedinformation the user device 104 may provide the discoverability examplefor the “skip ahead” voice action for output. For example, the userdevice 104 may receive the inducted information corresponding to thediscoverability example for the “skip ahead” voice action, and thereceived information may control the user device 104 to display atextual notification stating “Try Saying ‘Skip Ahead.” The presentationof the “Try Saying ‘Skip Ahead” discoverability example to the user 105can inform the user that the “skip ahead” voice action is an availablevoice action for the current status of the user device 104 andapplications running thereon. Thus, the user 105 may subsequentlyprovide the voice input “skip ahead,” and the voice input may beprocessed as discussed with respect to FIG. 1A to skip ahead by apredetermined amount of time in a song that the media player applicationis currently playing.

In some implementations, the discoverability example selector 160 mayselect multiple discoverability examples for presentation at the userdevice 104, and may transmit information corresponding to the selectedmultiple discoverability examples to the user device 104. For example,the discoverability example selector 160 may determine that the contextreceived from the context analysis engine 140 satisfies that specifiedby the discoverability example for the “skip ahead” voice action, aswell as a discoverability for a “pause” voice action for controlling themedia player application, and a “home” voice action associated with theoperating of the user device 104 that causes the user device 104 toreturn to a home screen. The discoverability example selector 160 mayprovide data for each of the discoverability examples to the user device104 such that all three of the discoverability examples is presented oravailable to be presented to the user 105.

FIG. 1C illustrates a voice action system 100 that enables applicationdevelopers to establish discoverability examples for voice actions, andfor discoverability examples to be provided to users. As discussedbelow, the system of FIG. 1C performs many of the same operationsdiscussed with respect to FIG. 1B. However, in FIG. 1C many of theseoperations are performed at a user device 104 as opposed to at the voiceaction system 100. By delegating some of the components and operationsperformed by the voice action system 100 in FIG. 1B to the user device104, discoverability examples may be provided to the user 105 even ifthe user device 104 is offline. This implementation also reduces theneeds of the user device 104 to contact the voice action system 100 eachtime discoverability examples are to be output at the user device 104,thereby reducing the network bandwidth used by the user device 104. Theability to provide discoverability examples without accessing a networkmay also reduce the power consumption incurred by providingdiscoverability examples, and may enable more rapid provision ofdiscoverability examples to users.

As shown in FIG. 1C, application developers 101 a-101 n may each submitinformation specifying discoverability examples for new voice actions tothe voice action system 100 using terminals 102 a-102 n as in FIG. 1B.The information specifying each submitted discoverability example maycorrespond to a voice action for a particular software application. Theinformation submitted to the voice action system 100 for a newdiscoverability example corresponding to a voice action may include, forexample, information specifying one or more trigger terms used totrigger the voice action, a context specified for the voice action,notification content to be presented to a user when the discoverabilityexample is output, or other information. Alternatively, the voice actionsystem 100 may receive information from the application developer 101a-101 n for establishing a new voice action, and the voice action system100 may generate candidate discoverability examples that the applicationdeveloper 101 a-101 n can select from. In such an implementation, thevoice action system 100 may present the candidate discoverabilityexamples to the application developer 101 a-101 n at their correspondingterminal 102 a-102 n, and may receive information indicating theselection of one or more of the candidate discoverability examples.

Based on the received information, the voice action system 100 generatesand stores discoverability examples at the voice action discoverabilityexample database 170. The voice action discoverability example database170 can include discoverability examples that correspond to voiceactions for controlling one or more different applications, operatingsystems, or devices.

As shown in FIG. 1C, appropriate discoverability examples that arestored at the voice action discoverability example database 170 areprovided to user devices, where they are stored at an applicationmetadata backend that is unique to each device. For example, the userdevice 104 may include an application metadata backend 180 that isconfigured to store discoverability examples that are pertinent to theuser device 104 and applications or an operating system installed on theuser device 104. The user device 104 may regularly communicate with thevoice action system 100 over one or more wired or wireless data pathwaysto identify discoverability examples that are pertinent to the userdevice 104, applications installed on the user device 104, and/or anoperating system of the user device 104. Discoverability examplesidentified as being relevant to the user device 104, applicationsinstalled at the user device 104, and/or the operating system of theuser device 104 can be retrieved from the voice action discoverabilityexample database 170 and stored at the application metadata backend 180of the user device 104.

For example, in the some implementations, the user device 104 may beequipped with an application interface 190 that is configured to receivediscoverability examples stored at the voice action discoverabilityexample database 170 that are identified as being relevant to the userdevice 104, applications installed at the user device 104, and/or theoperating system of the user device 104. The application interface 190may obtain the identified discoverability examples from the voice actiondiscoverability example database 170 and may store the identifieddiscoverability examples at the application metadata backend 180. Thevoice action system 100 may be configured to automatically identifydiscoverability examples that are relevant to the user device 104 orsoftware installed on the user device 104, and to provide relevantdiscoverability examples to the user device 104. For example, the voiceaction system 100 may provide relevant discoverability examples to theuser device 104 for storage at the application metadata backend 180 on aperiodic basis, in response to user input that requests thediscoverability examples be updated, in response to determining that astatus of the user device 104 has changed, in response to determiningthat different applications or versions of applications are installed atthe user device 104, in response to determining that a differentoperating system or version of an operating system is operating on theuser device 104, or in response to other events.

In addition to storing discoverability examples at the user device 104,the system of FIG. 1C also includes, at the user device 104, componentsdiscussed with respect to FIG. 1B for presenting discoverabilityexamples to a user 105. For example, the user device 104 shown in FIG.1C includes a context analysis engine 140 similar to the contextanalysis engine 140 of FIGS. 1A and 1B, as well as a discoverabilityexample selector 160 similar to the discoverability example selector 160of FIG. 1B. Additionally, the user device 104 may be capable ofgenerating transcriptions of voice inputs in a similar manner as thespeech recognition engine 130 of FIG. 1B.

The application interface 190 or other component of the user device 104may determine when discoverability examples should be provided foroutput at the user device 104. For example, a user 105 of the userdevice 104 may provide a voice input stating, “What voice commands can Iuse?” and the user device 104 may generate a transcription of the voiceinput. The application interface 190 may receive the transcription ofthe voice input, and may determine that the voice input is a request fordiscoverability examples. Alternatively, the application developer 190may otherwise determine to provide discoverability examples for outputat the user device 104. For example, the application interface 190 maydetermine that a user 105 has provided other input to the user device104, such as a press and hold feature on a button of the user device104, that requests discoverability examples for a current status of theuser device 104 or an application or operating system operating on theuser device 104. The application interface 190 may also determine toprovide discoverability examples based on a determination that a statusof the user device 104, an application installed on the user device 104,or an operating system of the user device 104 has changed. In someexamples, discoverability examples may be provided at the user device104 in response to determining that a previous voice input of the user105 does not match any known trigger term for a voice action, to informthe user 105 of trigger terms that may be used.

Although described above as being performed by the application interface190, in some implementations another component of the user device 104may determine that discoverability examples should be provided foroutput at the user device 104. For example, as shown in FIG. 1C, atranscription of the voice input “What voice commands can I say?” can beprovided to the discoverability example selector 160, and based on thetranscription the discoverability example selector 160 may determinethat discoverability examples should be provided for output at the userdevice 104. Similarly, the discoverability example selector 160 maydetermine to present discoverability examples at the user device 104based on other information, such as information indicating other userinput at the user device 104 or based on detecting that there has been achange in the status of the user device 104, an application installedand/or running on the user device 104, and/or an operating system of theuser device 104.

When the application interface 190 determines to provide discoverabilityexamples for output at the user device 104, the application interfacemay obtain contextual information for the user device 104 that indicatesa status of the user device 104, one or more applications installedand/or running on the user device 104, and/or an operating system of theuser device 104. Similar to the implementation discussed with respect toFIG. 1B, upon obtaining the contextual information, the applicationinterface 190 can provide the contextual information to the contextanalysis engine 140 where the contextual information is processed.

The context analysis engine 140 may obtain the context information andprocess the information to identify a context that is relevant toidentifying discoverability examples to output at the user device 104.For example, if the context analysis engine 140 receives contextualinformation from the application interface 190 that indicates that themedia player application is presently running in the foreground of theuser device 104, that the media player application is in an audio playermode, and that the battery life of the user device 104 is currently 50%,the context analysis engine 140 may determine that only the contextualinformation indicating that the media player application is running inthe foreground and that the media player application is in an audioplayer mode is relevant to selecting discoverability examples to presentat the user device 104. Therefore, the context analysis engine 140 mayprovide a context to the discoverability example selector 160 thatindicates that the media player application installed on the user device104 is operating in the foreground and is in an audio player mode, anddoes not indicate a battery life of the user device 104.

The discoverability example selector 160 can receive the context fromthe context analysis engine 140, and can use the received context toidentify discoverability examples stored at the application metadatabackend 180 to provide for output. For example, as discussed withrespect to FIG. 1B, the discoverability example selector 160 can comparethe received context with contexts specified by the discoverabilityexamples stored at the application metadata backend 180 to identify oneor more discoverability examples to provide for output. For example, thediscoverability example selector 160 may identify the discoverabilityexample for the “skip ahead” voice action based on determining that thecontext received from the context analysis engine 140 matches that ofthe discoverability example for the “skip ahead” voice action. In someimplementations, the discoverability example selector 160 may identifymultiple discoverability examples to provide for output at the userdevice 104. For example, the discoverability example selector 160 mayselect discoverability examples for the “skip ahead” voice action, a“pause” voice action for controlling the media player application, and a“home” voice action for controlling the user device 104 to return to ahome screen.

The discoverability example selector 160 can provide the selecteddiscoverability examples for output at the user device 104. For example,the discoverability example selector 160 may be able to provide theselected discoverability examples for output via the applicationinterface 190. As shown in FIG. 1C, for instance, the selecteddiscoverability example for the “skip ahead” voice action may be outputat the user device 104, thereby causing the textual notification “TrySaying ‘Skip Ahead” to be output at a display of the user device 104.

FIG. 2 depicts an example voice action system 200 that is configured toenable the establishment of voice actions and discoverability examplesfor voice actions. Briefly, the voice action system 200 includes avalidation engine 210 that has access to validation criteria 215, adiscoverability example induction engine 220, and a voice actiondiscoverability example database 235 that is configured to storediscoverability examples. The voice action system 200 may operate as aplatform offering a service or tool that enables an applicationdeveloper 201 to establish voice actions and discoverability examplesfor those voice actions via a terminal 202. In some implementations, theapplication developer 201 may establish voice actions according to themethods disclosed in U.S. patent application Ser. No. 15/057,453, filedMar. 1, 2016, which is hereby incorporated by reference in its entirety.

As shown in FIG. 2, the application developer 201 may submit informationto the voice action system 200 to define a new voice action. In someexamples, the information defining the voice action may be submitted asa grammar in a format that can be processed by the voice action system200 to generate an intent for the voice action. For example, theapplication developer 201 may enter information at the terminal 202 thatspecifies that a new voice action is to be established for the mediaplayer application. The application developer 201 may specify that thenew voice action uses the trigger phrase “skip ahead” to control themedia player application to skip ahead by a predetermined amount of timein a song that the media player application is currently playing. Theapplication developer 201 may further specify a context for the “skipahead” voice action such that the “skip ahead” voice action is onlycapable of being triggered when the media player application isoperating in the foreground of a user device, and only when operating inan audio player mode. The information submitted by the applicationdeveloper 201 may be in the form of a grammar that is capable of beingprocessed by the voice action system 200, or the information submittedby the application developer 201 may be converted into a grammar formatfor submission to the voice action system 200.

The information defining the new voice action can be submitted to thevoice action system 200 by the terminal 202 over one or more wired orwireless data pathways. The voice action system 200 can receive theinformation defining the new voice action at a validation engine 210that is configured to validate new voice actions submitted byapplication developers. For example, the validation engine 210 mayreceive a grammar defining a new voice action that has been submitted bythe application developer 201. To validate the new voice action, thevalidation engine 210 may access one or more validation criteria 215that can include one or more rules associated with defining a new voiceaction. The validation engine 210 may evaluate the information definingthe new voice action in view of the accessed validation criteria 215.

For the example “skip ahead” voice action shown in FIG. 2, thevalidation engine 210 may determine whether the media player applicationis an existing application, such that new voice actions can be createdfor the specified application. The validation engine 210 may access arule that specifies that a trigger phrase must be more than one spokensyllable in length, and may validate the trigger phrase “skip ahead”based on determining that the trigger phrase “skip ahead” is longer thanone spoken syllable. The validation rules may specify a list of possibleactions that the media player application can perform, and may validatethe specified action to skip ahead by a predetermined amount of time ina song that the media player application is currently playing based ondetermining that the media player application can skip ahead by apredetermined amount of time in a song currently playing in theapplication. The validation engine 210 may validate the contextspecified by the grammar to ensure that the context does not containcontradictions. For example, the validation engine may ensure that thespecified context does not require the application to be operating inthe foreground and also operating in the background for the new voiceaction to be enabled, since only one of those two conditions can besatisfied. Other validation criteria 215 may be applied to informationdefining a new voice action to determine whether the new voice actionsubmitted by the application developer 201 is valid and can be inductedto generate an intent for the new voice action.

Other forms of validation may be performed by the validation engine 210.For instance, the validation engine 210 may determine whether theapplication developer 201 is authorized to generate new voice actionsfor the specified application, may determine whether a fee required togenerate the new voice action has been paid, or may otherwise determinewhether a grammar submitted by an application developer 201 may resultin the creation of an intent for the new voice action.

Based on determining that the grammar or other information defining thenew voice action submitted by the application developer 201 is valid,the voice action system 200 can induct the information defining the newvoice action to generate an intent for the new voice action as discussedwith respect to FIG. 1A. The generated intent can be stored at a voiceaction database similar to the application voice action database 110,where the voice action may then be deployed by the application developer201 to enable the application for users having the application installedon their user devices. For example, the grammar or other informationdefining the “skip ahead” voice action may be inducted by the voiceaction system 200 to generate an intent for the “skip ahead” voiceaction, and the intent for the “skip ahead” voice action may be storedat an application voice action database. The application developer 201may deploy the “skip ahead” voice action to enable the “skip ahead”voice action for users who have the media player application installedon their user devices.

As shown in FIG. 2, in addition to generating an intent for the newvoice action, the voice action system 200 may also induct theinformation defining the new voice action to generate one or morecandidate discoverability examples for the new voice action. Forexample, the validated information defining the new voice action may besubmitted to the discoverability example induction engine 220, and thediscoverability example induction engine 220 can induct the informationdefining the new voice action to generate one or more candidatediscoverability examples for the new voice action.

In some implementations, the discoverability example induction engine220 may induct the information defining the new voice action to generateone or more candidate discoverability examples. The candidatediscoverability examples may be in a format that, when provided to auser device, can control or enable the user device to provide anotification specified by the discoverability example to be output atthe user device. For example, inducting the data defining the voiceaction may result in the generation of a particular data item or dataitem in a particular format that, when received by a user device ortriggered at a user device controls the user device to present atextual, image, video, audio, or other notification for output to informa user of the device of trigger terms that can be used to trigger theassociated voice action at the user device.

In some implementations, inducting the data defining the new voiceaction to generate a candidate intent can include generating one or moretextual phrases, spoken audio phrases, images, or videos that specify atrigger phrase for triggering the associated voice action. For example,the discoverability example induction engine 220 may receive the dataindicating the trigger phrase for the new voice action, and may generateone or more candidate phrases corresponding to one or more candidatediscoverability examples. In the example shown in FIG. 2, thediscoverability example induction engine 220 may generate candidatephrase such as “Try Saying ‘Skip Ahead’,” “Say ‘Skip Ahead’ to FastForward 30 Seconds,” “Say, ‘Okay Computer, Skip Ahead,” or any number ofother candidate phrases. The discoverability example induction engine220 may also generate, as candidate notifications for candidatediscoverability examples, spoken versions of the candidate phrases,candidate images that indicate the trigger phrase “skip ahead”associated with the new voice action, or candidate videos that indicatethe trigger phrase “skip ahead.”

In some implementations, a trigger phrase for a voice action may includeone or more placeholders, such as one or more enumerated types, and thediscoverability example induction engine 220 may generate candidatediscoverability examples associated with notifications that include theplaceholders. For example, a voice command may be associated with thetrigger phrase, “add % CurrentSong to favorites,” where “% CurrentSong”is a placeholder that refers to a song that is currently playing in themedia player application. The discoverability example induction engine220 may generate a candidate discoverability example that includes aphrase, “Try Saying, ‘Add % CurrentSong to Favorites’,” where theplaceholder may be replaced by a name of a song currently playing in themedia player application when the phrase is provided for output.

In some implementations, the candidate discoverability examplesgenerated by the discoverability example induction engine 220 also eachspecify the context when the new voice action is capable of beingtriggered, such that the discoverability examples for the new voiceaction are only capable of being output at a user device when a statusof the a user device, application running on the user device, oroperating system of the user device matches the context specified by thecorresponding voice action. In this way, discoverability examplesprovided to users in any particular situation are limited todiscoverability examples for voice actions that can be triggered at thattime.

As discussed previously, a context specifies one or more conditions thatmust be satisfied for a voice action to be enabled, i.e., such that thevoice action will not be triggered by a trigger phrase associated withthe voice action unless the context is also satisfied. The applicationdeveloper 201 can define a context as have one or more differentrequirements or conditions.

In some instances, a context may require a certain status of a userdevice, or may require a user device to have certain attributes. Forinstance, a context may specify whether the user device is powered on orlocked, or whether the user device has a camera, gyroscope, barometer,or other component or feature. Thus, for example, a voice action to takea picture using an application installed on a user device may not beenabled if contextual information received from the user deviceindicates that the user device does not have a camera.

In other examples, a context may require that specific applications areoperating in the foreground or background of a user device. For example,as shown in FIG. 2, the “skip ahead” voice action may only be enabledwhen the media player application is operating in the foreground of userdevice 204, but not if the media player application is closed or isoperating in the background of the user device 204. In other examples, avoice action may be defined with a context that enables the voice actionwhen an application is operating in the background. For instance, asocial network application may have an associated voice action to accepta request to connect with another user, and a user may be able totrigger the voice action to accept a request to connect with anotheruser even if the social network application is only operating in thebackground of the user device.

A context may additionally or alternatively require that a particularapplication is operating in a specific mode for a voice action to beenabled. A mode may be a particular activity or task that theapplication is executing. For example, an email application may bedetermined to be in an email write mode, a media player application maybe in an audio player mode, or a camera application may be in a cameramode or a photo album viewer mode. The user device may be able todetermine which of the modes a particular application is operating in,and may include that information in context information that is used todetermine whether a particular voice action is enabled.

Additionally, in some instances, a context may require that anapplication mode has a certain status. For example, a context mayindicate that a voice action to “pause” a movie may only be enabled whena media player application is in a movie player mode and when the statusof the application in the movie player mode is that the application iscurrently playing the movie. In some instances, a user device may not beable to determine the status of an application operating in a particularmode. In those instances, it may be necessary to configure theapplication to provide information indicating the status of theapplication in a particular mode. Thus, specifying such a condition in acontext for a particular application may require modifications to theapplication itself, in order for context information provided by theuser device to include the required status information.

In some examples, a context specified for a voice action may requirethat particular objects or types of objects are displayed on a screen ofa user device to enable the voice action. For example, a context mayspecify that a “save image” voice action is only enabled if an image isbeing output at the display of the user device, or may specify that a“highlight” voice action is only available if text is presented on thedisplay. In another example, a voice action to select a particular itemin a list, such as the voice action to “pick the first one” may only beavailable if context information indicates that a number “1” or a bulletpoint is being presented on the display of the user device, or if thereis a list of items being presented on the display. In some instances,the user device may not be capable of determining what information isbeing presented at its display at a given moment, e.g., when anapplication is in control of the display. Thus, if a context specifiesthat certain information or types of information must be output at thedisplay for a voice action to be enabled, then it may be necessary tomodify the application to provide that information. The user device canthen include the information indicating what is being output at thedisplay of the user device in contextual information that is used todetermine whether a specific voice action should be enabled.

In other instances, a context may require that a notification or aparticular type of notification has been output at a user device. Forexample, an email application that provides pop-up notifications tousers when a new email is received may have an associated voice actionto “read email” that is enabled when a new email notification is beingoutput to the display of a user device by the application. Thus, contextinformation may indicate whether a notification is being output to thedisplay of the user device, and that information may be used indetermining whether the “read email” voice action should be enabled.

In some examples, a context may require a user device be in a particulargeographic location for a voice action to be enabled. A user device maybe capable of determining its geographic location using cellular towertriangulation, based on accessing an internet connection that isassociated with a particular geographic location, using GlobalPositioning System (GPS) technology, or using other means. The userdevice may include information indicating its geographic location incontext information, and a voice action may be enabled based on thegeographic location satisfying a context's geolocation requirements. Asan example, a context associated with a voice action for a retailer'sapplication may specify that a certain voice action should only beprocessed if a user device having the retailer application is within arange of one of the retailer's stores. The voice action for the retailerapplication may be enabled based on context information from the userdevice indicating that the geographic location of the user devicecorresponds to a geographic location that is within the range of one ofthe retailer's stores.

A context defined by an application developer can also indicate that avoice action associated with the context is only enabled during certaintimes, dates, months, seasons, or when other temporal conditions aremet. For example, a context may specify that a certain voice action isonly enabled if context information received from a user device or fromanother information source satisfies a time condition. For example, avoice action for a banking application may be associated with a contextthat includes a temporal condition, such that the voice action is onlyenabled if context information indicates that a time when the voiceaction is submitted is between 6:00 AM and 10:00 PM.

A context may specify other requirements for enabling a voice action tobe triggered. For example, the voice action system 200 may have accessto information from sources other than a user device, or may be able toreceive information from a user device that is obtained from one or moreinformation sources. The information received from the other sources canbe required context information for enabling a voice action. Suchinformation can include, for example, weather information, emotionalinformation for a user, news information, stock market information, orother information. For instance, the voice action system 200 may becapable of accessing other information sources through one or more wiredor wireless network connections, e.g., an Internet connection or othernetwork connection to a server system. A context for a voice action mayspecify that the voice action is enabled only if weather information fora geographic area corresponding to the location of a relevant userdevice indicates that it is raining in that location. To check whetherthe context condition is met, the voice action system 200 may be able toaccess weather information for a known location of a user device overthe one or more network connections.

In some implementations, the discoverability example induction engine220 can generate multiple versions of a candidate discoverabilityexample corresponding to different operating systems, different types ofuser devices, or different versions of an application. Because oneparticular data type or format may not be used to output adiscoverability example at all types of devices, operating systems, orversions of an application, the discoverability example induction engine220 may generate multiple versions of a discoverability example. Thus,correct versions of a discoverability example can be provided todifferent user devices to ensure proper output of the discoverabilityexample at those user devices. Additionally or alternatively, in someimplementations a discoverability example may be modified for provisionat different user devices, operating systems, or versions of anapplication. For example a generated discoverability example may includean image notification in one format, e.g., using a particular size,resolution, color map, etc., and the image notification may be capableof being modified or formatted for presentation at different types ofuser devices, in different operating systems, or within differentversions of an application.

In some implementations, candidate discoverability examples can bepresented to the application developer 201 for selection. For example,upon generating candidate discoverability examples for a new voiceaction submitted by the application developer 201, the voice actionsystem 200 may provide information to the terminal 202 of theapplication developer 201 that enables the application developer 201 toselect specific discoverability examples that they would like toimplement for the new voice action. In the example shown in FIG. 2, thediscoverability example induction engine 220 may present information atthe terminal 202 indicating the candidate phrases “Try Saying ‘SkipAhead’,” “Say ‘Skip Ahead’ to Fast Forward 30 Seconds,” and “Say, ‘OkayComputer, Skip Ahead,” and the application developer 201 may select oneor more of the candidate phrases. For example, the application developermay select the candidate phrase “Try Saying ‘Skip Ahead,” indicatingthat they would like a discoverability example for the “skip ahead”voice action to be a textual notification that is output to a user thatsays “Try Saying ‘Skip Ahead.”

Additionally or alternatively, the application developer 201 may submitinformation defining discoverability examples for a voice action. Forexample, as discussed with respect to FIGS. 1B and 1C, the applicationdeveloper 201 may submit information to the voice action system 200 thatdefines a discoverability example for a voice action. The submittedinformation defining the discoverability example may specify the voiceaction to which the discoverability example pertains, such asinformation specifying the “skip ahead” voice action, may specify acontext when the discoverability example should be available for outputat user devices, such as the context specified for the “skip ahead”voice action, and may submit content for a notification that includesthe trigger term to be presented as the discoverability example for thevoice action. In the example shown in FIG. 2, the application developer201 may submit information to the voice action system 200 that specifiesthe “skip ahead” voice action, a context that the discoverabilityexample for the “skip ahead” voice action should only be available foroutput when the media player application is operating in the foregroundand is in an audio player mode, and may submit an audio clip stating“Try Saying ‘Skip Ahead’” to the voice action system 200. Other contentmay be submitted by the application developer 201, such as a textualphrase, image, video, or other content that can be provided for outputat a user device to inform a user of the device that the voice action toskip ahead by a predetermined amount of time in a song that the mediaplayer application is currently playing can be triggered by providing avoice input that states “skip ahead.” In some examples, less,additional, or different information may be required from theapplication developer 201 to specify a discoverability example. Forinstance, the application developer 201 may only be required to submitinformation indicating the voice action and content to be output as anotification associated with the discoverability example.

The voice action system 200 can receive the data indicating thecandidate discoverability examples selected by the application developer201, and can store the selected candidate discoverability examples at avoice action discoverability example database 235. The voice actionsystem 200 can also receive data defining one or more discoverabilityexamples defined by the application developer 201, can induct the datadefining the one or more discoverability examples to generate data itemsin the proper discoverability example format, and can store thediscoverability examples generated by the induction process at the voiceaction discoverability example database 235.

For example, based on receiving data indicating a selection of thediscoverability example including the textual phrase, “Try Saying ‘SkipAhead’,” the voice action system can store the discoverability exampleat the voice action discoverability example database 235. As shown inFIG. 2, the stored discoverability example can be a particular data itemor data in a particular format named “Example Y” that specifies the“skip ahead” voice action, the trigger phrase “skip ahead” for the voiceaction, the notification “Try Saying ‘Skip Ahead’” that is provided foroutput when the discoverability example is triggered, and the contextwhen the discoverability example is available for output requiring thatthe media player application is operating in the foreground and is in anaudio player mode.

Similarly, a discoverability example defined by the applicationdeveloper 201 can be inducted to generate an item of data in aparticular format for the discoverability example. In some examples, thediscoverability example defined by the application developer 201 may beinducted to generated one or more versions of the discoverabilityexample, such as versions of the discoverability example that correspondto different versions of the application to which the voice actionrelates, different devices, or different operating systems. The one ormore discoverability examples generated during the induction processperformed by the discoverability example induction engine 220 can beprovided and stored at the voice action discoverability example database235. For example, a discoverability example defined by the applicationdeveloper 201 and inducted to generate a discoverability example can bestored at the voice action discoverability example database 235 as“Example X.”

The voice action discoverability example database 235 can store multiplediscoverability examples that correspond to one or more voice actionsfor one or more applications. For example, the voice actiondiscoverability example database 235 may include multiplediscoverability examples for each of multiple different voice actionsthat have been developed for multiple different applications, devices,or operating systems. The voice action discoverability example database235 may be a structured table, such as a look-up table, a linked list, agraph comprising nodes and edges between nodes, or may be any other datastructure capable of storing discoverability examples such thatdiscoverability examples can later be identified and provided for aproper status of a user device, operating system, or application. Insome instances, each discoverability example in the voice actiondiscoverability example database 235 may be associated with informationspecifying the application to which the discoverability examplepertains, a version of the application that the discoverability exampleis compatible with, a device or devices that the discoverability exampleis compatible with, an operating system or operating systems that thediscoverability example is compatible with, or other informationpertinent to selecting a particular discoverability example, such thatappropriate discoverability examples can be identified in the voiceaction discoverability example database 235 without having to parse thedata included in the discoverability example itself for suchinformation. Such an arrangement may enable faster identification ofappropriate discoverability examples to provide for output.

The discoverability examples stored in the voice action discoverabilityexample database 235 can be provided to user devices to control orenable the user devices to output discoverability examples. Forinstance, in the implementation of FIG. 1B, one or more discoverabilityexamples stored in the voice action discoverability example database 235can be provided to a user device for output in response to receiving arequest for discoverability examples from the user device. Or, as shownin the implementation of FIG. 1C, one or more of the discoverabilityexamples in the voice action discoverability example database 235 can beprovided to a user device and stored at the user device, such that theymay subsequently be triggered for output at the user device.

In some implementations, before a discoverability example is capable ofbeing provided for output at a user device, the application developer201 may be capable of testing a new discoverability example and afterapproving of the discoverability example may deploy the discoverabilityexample to enable the discoverability example to be provided for outputat a user device. For example, the application developer 201 may becapable of testing or performing a test at the terminal 202 in which theapplication developer 201 may be shown an example of how thediscoverability example will be provided for output at a user device,such as how a notification of the discoverability example will appear ata display of a user device or will sound when played by a user device.In some implementations, the application developer 201 may designate oneor more other user devices separate from the terminal 202 where thediscoverability example can be tested, to determine how thediscoverability example appears or sounds when presented at differentuser devices. If the application developer 201 approves of thediscoverability example, the application developer 201 may provide inputat the terminal 202 to deploy the discoverability example, therebyenabling the discoverability example to be output at user devices.Additionally, in some implementations, the application developer 201 maybe capable of rescinding deployment of the discoverability example, suchthat the discoverability example is no longer capable of being providedfor output at user devices.

FIG. 3 depicts a voice action system 300 that is configured to presentdiscoverability examples at a user device 304 to inform a user 305 ofthe user device 304 of trigger phrases that can trigger voice actions.In some implementations, the voice action system 300 can be included inthe user device 304, such that the user device 304 can providediscoverability examples for output to the user 305 withoutcommunicating with another system. In other examples, the voice actionsystem 300 may be separate from the user device 304, and the user device304 may communicate with the voice action system 300 over one or morewired or wireless data pathways when providing discoverability examplesfor output.

Briefly, the voice action system 300 can include a speech recognitionengine 330 similar to the speech recognition engine 130 of FIGS. 1A and1B, a context analysis engine 340 similar to the context analysis engine140 of FIGS. 1A to 1C, a matcher 350, a disambiguation engine 360, and aformatting engine 380. The matcher 350 may have access to an applicationmetadata backend 310 that includes one or more discoverability examplesthat are capable of being provided for output at the user device 304.The disambiguation engine 360 may have access to a user activity history370 that includes information indicating past operations performed atthe user device 304. Additionally, the formatting engine 380 may haveaccess to user device information 390 that indicates informationrelevant to the formatting of a discoverability example for output atthe user device 304. In some implementations, such as when the voiceaction system 300 is included in the user device 104, the voice actionsystem 300 may include an application interface (not shown) similar tothe application interface 190 of FIG. 1C.

Discoverability examples may be provided for output at the user device304 in response to determining that the user 305 has requesteddiscoverability examples or in response to determining that a conditionassociated with providing discoverability examples for output has beenmet. For example, as shown in FIG. 3, the user 305 may provide the voiceinput “What voice commands can I say?” to the user device 304. Audiodata corresponding to the voice input may be provided to the speechrecognition engine 330, and a transcription “What voice commands can Isay?” may be generated based on the audio data. The transcription “Whatvoice commands can I say?” may be interpreted, for example, by thematcher 350 of the voice action system 300, as a request fordiscoverability examples.

In other instances, different user input, such as different voiceinputs, a selection of a “help” button, a press-and-hold input at acontrol of the user device 304, or other user inputs may result in thevoice action system determining to provide discoverability examples foroutput at the user device 304. In still other instances, otherinformation cause the voice action system 300 to determine to providediscoverability examples, such as information indicating that a statusof the user device 304, an application operating on the user device 304,or an operating system of the user device 304 has changed. In someexamples, discoverability examples may be provided for output at theuser device 304 based on determining that the user 305 has provided avoice input to the user device 304 that does not match any particularvoice action trigger phrase. In such an example, discoverabilityexamples provided to the user 305 may be selected based on determiningthat the discoverability examples may correspond to an action that theuser 305 intended to perform at the user device 304.

Based on determining to provide discoverability examples for output atthe user device 304, contextual information indicating a status of theuser device 304, one or more applications installed on user device 304,or an operating system of the user device 304 can be provided to thevoice action system 300. For example, the voice action system 300 maydetermine to provide discoverability examples for output at the userdevice 104, and in response may obtain contextual information. In otherimplementations, the voice action system 300 may determine to providediscoverability examples at the user device 304 in response to receivingcontextual information. For example, the voice action system 300 maydetermine to provide discoverability examples for output at the userdevice 304 in response to one or more hardware components of the userdevice 304, one or more applications installed on the user device 304,or an operating system of the user device 304 providing information tothe voice action system 300 indicating their status. In someimplementations, the voice action system 300 may obtain or be providedwith contextual information at regular intervals or continuously.

The contextual information can be received by the context analysisengine 340, where the context analysis engine 340 may process thecontextual information to determine a relevant context. For example, asdiscussed previously, the context analysis engine 340 can receivecontextual information that indicates a status of numerous components ofthe user device 304, numerous applications installed on the user device304, or one or more operating systems operating on or associated withthe user device 304. The context analysis engine 340 can determine arelevant context of the user device 304 from the received information.The context analysis engine 340 may filter unnecessary contextualinformation to get the relevant context, can interpret the receivedcontextual information to determine a relevant context, or can otherwiseuse the received contextual information to determine a relevant context.

For the example shown in FIG. 3, for instance, the context analysisengine 340 may receive contextual information that indicates that themedia player application is operating in the foreground of the userdevice 304, that the media player application is operating in an audioplayer mode, and that a battery life of the user device 304 is 50%. Thecontext analysis engine 340 may filter out the battery life contextualinformation to generate a relevant context that indicates only that themedia player application is operating in the foreground and is in anaudio player mode. In another example, the context analysis engine 340receives contextual information indicating that the media playerapplication is operating in the foreground of the user device 304, thata headphone jack of the user device 304 is providing output, and that adisplay of the user device 304 is currently dimmed. The context analysisengine 340 may interpret the received contextual information todetermine a relevant context. For instance, the context analysis engine340 may determine that the media player application operating in theforeground is likely in an audio player mode, since the headphone jackis providing sound output while the display is dimmed.

The relevant context determined by the context analysis engine 340 isprovided to the matcher 350, where the matcher 350 identifiesdiscoverability examples that may be provided for output at the userdevice 304 given the current status of the user device 304, applicationsinstalled on the user device 304, or an operating system of the userdevice 304. The matcher 350 may select those discoverability examplesthat are associated with contexts that match the relevant contextdetermined by the matcher 350. To determine discoverability examplesthat match the relevant context received from the context analysisengine 340, the matcher 350 compares the relevant context to contextsspecified by one or more discoverability examples stored in theapplication metadata backend 310. For example, as discussed with respectto FIG. 2, the application metadata backend 310 may store numerousdiscoverability examples that may be associated with numerous voiceactions pertaining to numerous different applications, devices, oroperating systems. Each discoverability example in the applicationmetadata backend 310 may specify a context indicating when thecorresponding voice action is available to be triggered, which alsodefines when the discoverability example is available to be provided foroutput at a user device. By comparing the received context with thecontexts specified by the discoverability examples in the applicationmetadata backend 310, the matcher 350 identifies a set of candidatediscoverability examples that are eligible to be provided for output atthe user device 304.

In the example shown in FIG. 3, for instance, the matcher 350 maycompare the context indicating that the media player application isoperating in the foreground and is in an audio player mode to multiplediscoverability examples stored in the application metadata backend 310.Based on the comparison, the matcher may identify a set of fourdiscoverability examples that correspond to voice actions that can betriggered by a user given the present context. These discoverabilityexamples may include, for example, a discoverability example for the“skip ahead” voice action, a discoverability example for a “pause” voiceaction for controlling the media player application to pause a songplaying in the audio player application, a discoverability example for a“search for similar songs” voice action that controls the media playerapplication to search a database or the Internet for songs that aredetermined to be similar to a song currently playing in the media playerapplication, and a discoverability example for a “home” voice actionthat controls the user device 304 to return to a home screen of the userdevice 304 (e.g., a desktop or menu screen that the operating systempresents to users at a display of the user device 304).

The matcher 350 can identify the candidate discoverability examples andcan provide the candidate discoverability examples to the disambiguationengine 360. In some implementations, providing the candidatediscoverability examples to the disambiguation engine 360 may requiresending data items corresponding to the candidate discoverabilityexamples to the matcher 350. In other implementations, thedisambiguation engine 360 may be capable of accessing the candidatediscoverability examples at the application metadata backend 310, suchthat the matcher 350 need only provide information to the disambiguationengine 360 that identifies the candidate discoverability examples,without needing to send the items of data corresponding to the candidatediscoverability examples to the disambiguation engine 360. In someexamples, identifying a candidate discoverability example includesidentifying one or more versions of the candidate discoverabilityexample as candidate discoverability examples. For example, the “skipahead” voice action may be associated with multiple discoverabilityexamples that each specify a context corresponding to the contextreceived from the context analysis engine 340, such as a textualnotification discoverability example and a spoken word audionotification discoverability example, and both the textual and spokenword audio notifications may be provided or identified to thedisambiguation engine 360.

The disambiguation engine 360 can receive the candidate discoverabilityexamples or information identifying the candidate discoverabilityexamples from the matcher 350, and can select one or morediscoverability examples from among the candidate discoverabilityexamples to provide for output to the user device 304. In someimplementations, the disambiguation engine 360 may selectdiscoverability examples from among the candidate discoverabilityexamples based on details of a user activity history 370, based on thecapabilities of the user device 304 to present discoverability examples,or based on the status of the user device 304. The number ofdiscoverability examples selected by the disambiguation engine 360 candepend on, for example, the type of discoverability examples that to bepresented to a user, e.g., whether the discoverability examples outputto the user 305 are textual, images, audio, video, etc. The number ofdiscoverability examples selected may also depend on the capabilities ofthe user device 304, for example, based on a display size of the userdevice 304 that could be a limiting factor in the quantity of textual orimage notifications that can be presented at the user device 304. Otherfactors may influence the selection of discoverability examples by thedisambiguation engine 360. For example, in some implementations, thedisambiguation engine may receive information indicating userpreferences for the number of discoverability examples to be displayed,a size of a display of the user device 304, or other information, andthe received information may affect the specific discoverabilityexamples selected or the number of discoverability examples selected bythe disambiguation engine 360.

For example, the disambiguation engine 360 may have access to a userhistory 370 that indicates operations previously performed at the userdevice 304, and the disambiguation engine 360 may select discoverabilityexamples to provide for output based on the user history 370. In someimplementations, the user history 370 may indicate operations previouslyperformed at the user device 304 in the media player application,operations previously performed at the user device 304 when a status ofthe user device 304 matches the current context, when a status of themedia player application matches the current context, when a user hasrequested discoverability examples indicating available voice actions,or may otherwise indicate a history of user operations performed at theuser device 304. The disambiguation engine 360 may rely upon the userhistory 370 to identify discoverability examples to provide for outputat the user device 304. For example, the disambiguation engine 360 maydetermine that a user has previously skipped ahead (e.g., fastforwarded) in a song previously while operating the media playerapplication in the foreground and in an audio player mode, and maytherefore select the discoverability example for the “skip ahead” voiceaction as a discoverability example to be output at the user device 304.

The disambiguation engine 360 may otherwise utilize the user activityhistory 370 in selecting discoverability examples from among thecandidate discoverability examples identified by the matcher 350. Forexample, the disambiguation engine 360 may access the user activityhistory 370, and may determine to select a particular candidatediscoverability example based on the user activity history 370indicating that a user has previously performed a voice actioncorresponding to the particular candidate discoverability example, maydetermine not to select a particular candidate discoverability examplebased on the user activity history 370 indicating that a user haspreviously performed a voice action corresponding to the particularcandidate discoverability example, may determine to select theparticular candidate discoverability example based on determining that auser has previously or recently entered voice input that is similar to atrigger phrase associated with the particular candidate discoverabilityexample, may determine to select a particular candidate discoverabilityexample based on determining that a user has performed operationspreviously at the user device 304 that matches an action that theparticular candidate discoverability example is associated with, or thedisambiguation engine 360 may otherwise utilize the user activityhistory 370 in the selection of particular candidate discoverabilityexamples.

In some implementations, the disambiguation engine 360 may utilize otheravailable information to select discoverability examples. For example,the disambiguation engine 360 may have access to information about theuser device 304, such as user device information 390, or a status of theuser device 304, such as contextual information received from the userdevice 304, and may select discoverability examples based on theavailable information. For instance, the disambiguation engine 360 mayaccess information indicating that the user device 304 does not have adisplay, and therefore the disambiguation engine 360 may select onlyaudio discoverability examples, since textual, image, or videodiscoverability examples cannot be effectively provided for output atthe user device 304. Alternatively, if the disambiguation engine 360accesses information indicating that the user device 304 has a displayand is currently in a “silent” mode, the disambiguation engine 360 mayselect candidate discoverability examples that are textual or imagediscoverability examples, and not audio or video discoverabilityexamples since audio for those discoverability examples may not beoutput while the user device 304 is in “silent” mode. The disambiguationengine 360 may rely on other information, such as user preferences thatindicate the preferences of the user 305 to receive discoverabilityexamples of a certain type, in selecting from among the candidatediscoverability examples.

In some implementations, the disambiguation engine 360 may select fromamong the candidate discoverability examples based on the accessedinformation, such as user activity history 370, based on assigning aranking or relevance score to the candidate discoverability examples.For instance, the disambiguation engine 360 may use the accessedinformation to rank the discoverability examples according to theirperceived relevance to the status of the user device 304, an expectedintent of the user 305, or other criteria, and may select from among thecandidate discoverability examples based on the ranking. Additionally,in some implementations, one or more discoverability examples may bediscoverability examples that are always presented to users at the userdevice 304. For example, a discoverability example for a “back” voiceaction that controls the user device 304 to return to previous screenmay always be selected for output, or may always be selected for outputwhen a particular context associated with the “back” voice action issatisfied.

In some implementations, the disambiguation engine 360 may selectdifferent groups of candidate discoverability examples that may beprovided for output at the user device 304 in different ways. Forinstance, the disambiguation engine 360 may identify some candidatediscoverability examples to be output as audio notifications, and othercandidate discoverability examples to be output as textualnotifications. In some examples, the disambiguation engine 360 maydetermine that some discoverability examples should be output to aprimary discoverability example window or pane of a user interfacedisplayed at the user device 304, and may select other candidatediscoverability examples to include in a drop down menu, in a “viewmore” area of the user interface, or in other separate regions of a userinterface.

The selected candidate discoverability examples or informationidentifying the selected discoverability examples may be transmitted tothe formatting engine 380, where the formatting engine 380 can formatthe selected discoverability examples for output at the user device 304.For example, the formatting engine 380 may have access to user deviceinformation 390 that indicates characteristics of the user device 304that are pertinent to presenting discoverability examples at the userdevice 304, and may prepare the discoverability examples for output atthe user device 304 based on the user device information 390. Userdevice information 390 can include, for example, a display size,resolution, color spectrum, refresh rate, or other parameters, an audiooutput frequency range or other speaker or headphone jack outputparameters, application programming interface protocols or input/outputformats, or other information relevant to provide discoverabilityexamples for output at the user device 304.

The formatting engine 380 can receive or access the candidatediscoverability examples selected by the disambiguation engine 370 andcan format the selected candidate discoverability examples for output atthe user device 304. For example, the formatting engine 380 may receivethe selected candidate discoverability example data items, or can accessthe selected candidate discoverability examples at the applicationmetadata backend 310, and based on formatting the selected candidatediscoverability examples, can provide the formatted discoverabilityexamples for output at the user device 304. For instance, based ondisambiguation engine 360 selecting the candidate discoverabilityexamples for the “skip ahead” voice action, the “pause” voice action,and the “home” voice action, the formatting engine 380 can format theselected candidate discoverability examples and can control the userdevice 304 to provide the formatted discoverability examples for output.For instance, if each of the selected candidate discoverability examplesis a textual notification that indicates the trigger terms used totrigger the voice actions corresponding to the selected discoverabilityexamples, the formatting engine 380 may format the textual notificationsand can cause the formatted textual notifications to be provided foroutput at a display of the user device 304. Thus, the formatteddiscoverability examples may be output at the user device 304 as shownin FIG. 3, by presenting the phrase “Try Saying:” followed by thetrigger phrases used to trigger each of the “skip ahead,” “pause,” and“home” voice actions.

The user 305 may be presented with the textual notifications identifyingthe trigger phrases “skip ahead,” “pause,” and “home,” and based on thediscoverability examples being provided at the user device 304, the user305 may provide a voice input to trigger one of the voice actionscorresponding to the suggested trigger phrases. For example, the user305 may provide the voice input “skip ahead” in response to beingpresented with the discoverability examples to control the media playerapplication operating in the foreground of the user device 304 to skipahead by a predetermined amount of time in a song that the media playerapplication is currently playing.

FIG. 4 is a flowchart of an example process 400 for establishing andproviding discoverability examples for output at a user device. In someimplementations, the process 400 may be performed by a voice actionsystem, such as the voice action system 100 of FIGS. 1A to 1C.

The voice action system receives data specifying trigger terms thattrigger a software application to perform a new voice action, and acontext that specifies a status of the software application when the newvoice action can be triggered (402). For example, an applicationdeveloper 101 a-101 n using a terminal 102 a-102 n may submitinformation to the voice action system 100 for defining a new voiceaction for an application that is installed at one or more user devices104. The information submitted by the application developer 101 a-101 nmay specify a context that indicates a status of the softwareapplication when the new voice action can be triggered at a user device104. The information may further specify trigger terms that a user 105can speak into a user device 104 to trigger the voice action.

For example, an application developer 101 a-101 n may submit informationto the voice action system 100 that defines a new “skip ahead” voiceaction for a media player application that controls the media playerapplication to skip ahead by a predetermined amount of time in a songthat the media player application is currently playing. The submittedinformation may include information indicating that the trigger phrase“skip ahead” is to be used to trigger the new voice action, and that thevoice action can be triggered only when the media player application isoperating in the foreground of the user device 104 and is operating inan audio player mode. The submitted information may include otherinformation as well, such as information indicating the action to beperformed in response to the voice action being triggered, or otherinformation.

The voice action system receives data defining a discoverability examplefor the new voice action, wherein the data defining the discoverabilityexample comprises one or more of the trigger terms that trigger thesoftware application to perform the new voice action when a status ofthe software application satisfies the specified context (404). Forexample, the application developer 101 a-101 n may submit information tothe voice action system 100 that specifies a discoverability example forthe new voice action. The information submitted by the applicationdeveloper 101 a-101 n and received by the voice action system 100 mayspecify one or more of the trigger terms that can be used by a user 105to trigger the new voice action at the user device 104. In this way, theapplication developer 101 a-101 n can specify a discoverability examplethat can cause a notification to be provided for output at the userdevice 104 when a status of the software application installed on theuser device 104 satisfies the specified context for the new voiceaction, where the notification presents the one or more of the triggerterms to the user 105 to inform the user 105 of the trigger terms thatthey can use to trigger the new voice action.

In some implementations, the information defining the new voice actionmay be in a particular required format that enables user devices to usethe discoverability example to provide a notification of the one or moretrigger terms. In other implementations, the voice action system 100 mayreceive information from the application developer 101 a-101 n thatidentifies the one or more trigger terms for the new voice action, orother information, but that is not in the particular required format. Togenerate a discoverability example in those instances, the voice actionsystem 100 may induct the received data to generate data defining thediscoverability example, where the data defining the discoverabilityexamples generated through the induction process is in the particularrequired format. In other implementations, the voice action system 100may generate the discoverability example based only on the receivedinformation specifying the new voice action, such as the informationspecifying trigger terms that trigger the software application toperform the new voice action. In other examples, the voice action system100 may generate the discoverability example based on the receivedinformation specifying the new voice action and based on otherinformation that specifies information about the discoverability examplethat is determined by the voice action system 100 or received at thevoice action system 100 from the application developer 101 a-101 n. Suchinformation can include, for instance, the content of the notificationto associate with the discoverability example. In other examples, thevoice action system 100 may determine one or more candidatediscoverability examples, and receiving the data defining thediscoverability example may involve receiving a selection by theapplication developer 101 a-101 n of a particular one of the candidatediscoverability examples.

For example, the voice action system 100 may receiving information fromthe application developer 101 a-101 n that defines a discoverabilityexample for the “skip ahead” voice action, where the data defining thediscoverability example specifies the trigger term “skip ahead” thattriggers the media player application to skip ahead by a predeterminedamount of time in a song that the media player application is currentlyplaying. The information received from the application developer 101a-101 n may be in a particular required format, or the voice actionsystem 100 may induct the information specifying the discoverabilityexample for the “skip ahead” voice action to generate a discoverabilityexample having the particular required format. In other examples, thevoice action system 100 may induct the information specifying the “skipahead” voice action itself, i.e., without receiving other informationseparately defining a discoverability example for the “skip ahead” voiceaction, to generate the data defining the “skip ahead” voice action. Inother implementations, the voice action system 100 may determinecandidate notifications for the “skip ahead” voice action based on thereceived information, and the application developer 101 a-101 n mayselect a particular candidate. The voice action system 100 may receiveinformation defining the selected candidate discoverability example, ormay receive information indicating the selection of the particularcandidate and, in response to the selection, may generate adiscoverability example for the “skip ahead” voice action according tothe selection. The generated discoverability example can includeinformation for a notification, such as a textual, image, audio, orvideo notification, that indicates the trigger term “skip ahead” used totrigger the voice action. In some examples, the application developer101 a-101 n may submit additional information that includes notificationcontent, and the voice action system 100 can generate a discoverabilityexample for the “skip ahead” voice action that includes the notificationcontent.

In some implementations, the data defining the discoverability exampleis associated with the software application at the voice action system100, to enable a user device 104 having the software applicationinstalled to provide the notification for output when a context of thesoftware application installed on the user device 104 satisfies thespecified context. For example, the voice action system 100 may storethe discoverability example at a voice action discoverability database170 in association with the software application. Once stored inassociation with the software application, the discoverability examplemay be provided for output to a user 105 of a user device 104 when acontext of the software application satisfies the context specified forthe new voice action.

The voice action system receives, from a user device having the softwareapplication installed, a request for discoverability examples for thesoftware application (406). For example, once the discoverabilityexample is stored at the voice action discoverability example database170, as shown in FIG. 1C, the voice action system 100 may receive arequest from the user device 104 for discoverability examples for thesoftware application. The user device 104 might request discoverabilityexamples for the software application based on any number of reasons.For example, the user device 104 may request discoverability examplesfor the software application installed at the user device 104 based ondetermining that a status of the software application has changed, mayrequest discoverability examples for the application based on a user 105of the user device 104 launching the software application or bringingthe software application to the foreground of the user device 104, mayrequest discoverability examples for the application based on a periodicschedule or a schedule set by the user 105, or may otherwise requestdiscoverability examples for the software application from the voiceaction system 100. In some examples, requests for discoverabilityexamples received from the user device 104 may include contextualinformation indicating a status of the software application installed atthe user device 104, such that the voice action system 100 may utilizethe contextual information in selecting discoverability examples toprovide to the user device 104.

The voice action system provides the data defining the discoverabilityexample to the user device in response to the request, wherein the userdevice is configured, based at least on the data defining thediscoverability example, to provide a notification of the one or more ofthe trigger terms when a status of the software application satisfiesthe specified context (408). For example, in response to the requestreceived from the user device 104, the voice action system 100 mayprovide data defining the discoverability example for the new voiceaction to the user device 104 for storage at the user device 104, suchas at the application metadata backend 180 of the user device 104. Insome implementations, as shown in FIG. 1B, the voice action system 100may be capable of determining that contextual information received fromthe user device 104, e.g., as the request for discoverability examplesor along with a request for discoverability examples, satisfies thecontext specified for the new voice action, and may therefore determineto provide the data defining the discoverability example for the newvoice action to the user device 104 to control or trigger output of anotification associated with the discoverability example at the userdevice 104. In other examples, as shown in FIG. 1C, once the voiceaction system 100 may provide the data defining the discoverabilityexample to the user device 104 in response to the received request, andmay store the data defining the discoverability example in associationwith the new voice action at the application metadata backend 180.Storing the data defining the discoverability example at the applicationmetadata backend 180 may configure the user device 104 to output anotification associated with the discoverability example. For example,when the user device 104 determines that a status of the softwareapplication installed on the user device 104 satisfies the contextspecified for the new voice action, the user device 104 may provide anotification of the one or more trigger terms used to trigger the newvoice action for output at the user device 104.

For instance, the discoverability example for the “skip ahead” voiceaction may be stored at the voice action discoverability exampledatabase 170 in association with the media player application. Whencontextual information received by the voice action system 100 from theuser device 104 with or as the request for discoverability examples isdetermined to satisfy the context specified for the “skip ahead” voiceaction, the discoverability example for the “skip ahead” voice action isprovided to the user device 104. The discoverability example received bythe user device 104 causes the textual notification “Try Saying ‘SkipAhead’” to be provided for output at the user device 104. In anotherexample, the voice action system 100 can provide data defining adiscoverability example for the “skip ahead” voice action to the userdevice 104 in response to a request for discoverability examples. Theuser device 104 can store the discoverability example for the “skipahead” voice action, for example, at the application metadata backend180 or by caching the discoverability example for the “skip ahead” voiceaction in a cache memory of the user device 104. The user device 104 maythen be capable of providing the textual notification “Try Saying ‘SkipAhead’” for output when a determination is made that the status of themedia player application satisfies the context specified for the “skipahead” voice action. For example, the textual notification may bepresented in a region of a user interface displayed at the user device104 that is configured to present discoverability examples for voiceactions. Alternatively, the notification may be presented in a searchresults page displayed at the user device 104, may be provided foroutput in a separate window in a user interface displayed at the userdevice 104, may be provided as audio, an image, or video at the userdevice 104, or may otherwise be provided for output at the user device104.

A number of implementations have been described. Nevertheless, it willbe understood that various modifications may be made without departingfrom the spirit and scope of the disclosure. For example, various formsof the flows shown above may be used, with steps re-ordered, added, orremoved. Accordingly, other implementations are within the scope of thefollowing claims.

For instances in which the systems and/or methods discussed here maycollect personal information about users, or may make use of personalinformation, the users may be provided with an opportunity to controlwhether programs or features collect personal information, e.g.,information about a user's social network, social actions or activities,profession, preferences, or current location, or to control whetherand/or how the system and/or methods can perform operations morerelevant to the user. In addition, certain data may be anonymized in oneor more ways before it is stored or used, so that personallyidentifiable information is removed. For example, a user's identity maybe anonymized so that no personally identifiable information can bedetermined for the user, or a user's geographic location may begeneralized where location information is obtained, such as to a city,ZIP code, or state level, so that a particular location of a user cannotbe determined. Thus, the user may have control over how information iscollected about him or her and used.

While the foregoing embodiments have been predominantly described withreference to the development of voice actions for use with applicationsinstalled on user devices, the described features may also be used withrespect to machines, other devices, robots, or other systems. Forexample, the voice action system 100 of FIGS. 1A to 1C may be utilizedto develop and implement voice actions and discoverability examples forinteracting with machinery, where the machinery has an associatedcomputing system, may be used to develop and implement voice actions forinteracting with a robot or system having robotic components, may beused to develop and implement voice actions for interacting withappliances, entertainment systems, or other devices, or may be used todevelop and implement voice actions for interacting with a vehicle orother transportation system.

Embodiments and all of the functional operations described in thisspecification may be implemented in digital electronic circuitry, or incomputer software, firmware, or hardware, including the structuresdisclosed in this specification and their structural equivalents, or incombinations of one or more of them. Embodiments may be implemented asone or more computer program products, i.e., one or more modules ofcomputer program instructions encoded on a computer readable medium forexecution by, or to control the operation of, data processing apparatus.The computer readable medium may be a machine-readable storage device, amachine-readable storage substrate, a memory device, a composition ofmatter effecting a machine-readable propagated signal, or a combinationof one or more of them. The term “data processing apparatus” encompassesall apparatus, devices, and machines for processing data, including byway of example a programmable processor, a computer, or multipleprocessors or computers. The apparatus may include, in addition tohardware, code that creates an execution environment for the computerprogram in question, e.g., code that constitutes processor firmware, aprotocol stack, a database management system, an operating system, or acombination of one or more of them. A propagated signal is anartificially generated signal, e.g., a machine-generated electrical,optical, or electromagnetic signal that is generated to encodeinformation for transmission to suitable receiver apparatus.

A computer program (also known as a program, software, softwareapplication, script, or code) may be written in any form of programminglanguage, including compiled or interpreted languages, and it may bedeployed in any form, including as a stand alone program or as a module,component, subroutine, or other unit suitable for use in a computingenvironment. A computer program does not necessarily correspond to afile in a file system. A program may be stored in a portion of a filethat holds other programs or data (e.g., one or more scripts stored in amarkup language document), in a single file dedicated to the program inquestion, or in multiple coordinated files (e.g., files that store oneor more modules, sub programs, or portions of code). A computer programmay be deployed to be executed on one computer or on multiple computersthat are located at one site or distributed across multiple sites andinterconnected by a communication network.

The processes and logic flows described in this specification may beperformed by one or more programmable processors executing one or morecomputer programs to perform functions by operating on input data andgenerating output. The processes and logic flows may also be performedby, and apparatus may also be implemented as, special purpose logiccircuitry, e.g., an FPGA (field programmable gate array) or an ASIC(application specific integrated circuit).

Processors suitable for the execution of a computer program include, byway of example, both general and special purpose microprocessors, andany one or more processors of any kind of digital computer. Generally, aprocessor will receive instructions and data from a read only memory ora random access memory or both.

The essential elements of a computer are a processor for performinginstructions and one or more memory devices for storing instructions anddata. Generally, a computer will also include, or be operatively coupledto receive data from or transfer data to, or both, one or more massstorage devices for storing data, e.g., magnetic, magneto optical disks,or optical disks. However, a computer need not have such devices.Moreover, a computer may be embedded in another device, e.g., a tabletcomputer, a mobile telephone, a personal digital assistant (PDA), amobile audio player, a Global Positioning System (GPS) receiver, to namejust a few. Computer readable media suitable for storing computerprogram instructions and data include all forms of non volatile memory,media and memory devices, including by way of example semiconductormemory devices, e.g., EPROM, EEPROM, and flash memory devices; magneticdisks, e.g., internal hard disks or removable disks; magneto opticaldisks; and CD ROM and DVD-ROM disks. The processor and the memory may besupplemented by, or incorporated in, special purpose logic circuitry.

To provide for interaction with a user, embodiments may be implementedon a computer having a display device, e.g., a CRT (cathode ray tube) orLCD (liquid crystal display) monitor, for displaying information to theuser and a keyboard and a pointing device, e.g., a mouse or a trackball,by which the user may provide input to the computer. Other kinds ofdevices may be used to provide for interaction with a user as well; forexample, feedback provided to the user may be any form of sensoryfeedback, e.g., visual feedback, auditory feedback, or tactile feedback;and input from the user may be received in any form, including acoustic,speech, or tactile input.

Embodiments may be implemented in a computing system that includes aback end component, e.g., as a data server, or that includes amiddleware component, e.g., an application server, or that includes afront end component, e.g., a client computer having a graphical userinterface or a Web browser through which a user may interact with animplementation, or any combination of one or more such back end,middleware, or front end components. The components of the system may beinterconnected by any form or medium of digital data communication,e.g., a communication network. Examples of communication networksinclude a local area network (“LAN”) and a wide area network (“WAN”),e.g., the Internet.

The computing system may include clients and servers. A client andserver are generally remote from each other and typically interactthrough a communication network. The relationship of client and serverarises by virtue of computer programs running on the respectivecomputers and having a client-server relationship to each other.

While this specification contains many specifics, these should not beconstrued as limitations on the scope of the disclosure or of what maybe claimed, but rather as descriptions of features specific toparticular embodiments. Certain features that are described in thisspecification in the context of separate embodiments may also beimplemented in combination in a single embodiment. Conversely, variousfeatures that are described in the context of a single embodiment mayalso be implemented in multiple embodiments separately or in anysuitable subcombination. Moreover, although features may be describedabove as acting in certain combinations and even initially claimed assuch, one or more features from a claimed combination may in some casesbe excised from the combination, and the claimed combination may bedirected to a subcombination or variation of a subcombination.

Similarly, while operations are depicted in the drawings in a particularorder, this should not be understood as requiring that such operationsbe performed in the particular order shown or in sequential order, orthat all illustrated operations be performed, to achieve desirableresults. In certain circumstances, multitasking and parallel processingmay be advantageous. Moreover, the separation of various systemcomponents in the embodiments described above should not be understoodas requiring such separation in all embodiments, and it should beunderstood that the described program components and systems maygenerally be integrated together in a single software product orpackaged into multiple software products.

In each instance where an HTML file is mentioned, other file types orformats may be substituted. For instance, an HTML file may be replacedby an XML, JSON, plain text, or other types of files. Moreover, where atable or hash table is mentioned, other data structures (such asspreadsheets, relational databases, or structured files) may be used.

Thus, particular embodiments have been described. Other embodiments arewithin the scope of the following claims. For example, the actionsrecited in the claims may be performed in a different order and stillachieve desirable results.

What is claimed is:
 1. A computer-implemented method comprising: receiving, by a voice action system, data specifying trigger terms that trigger a software application to perform a new voice action and a context that specifies a status of the software application when the new voice action can be triggered; receiving, by the voice action system, data defining a discoverability example for the new voice action, wherein the data defining the discoverability example comprises one or more of the trigger terms that trigger the software application to perform the new voice action when a status of the software application satisfies the specified context; receiving, by the voice action system from a user device having the software application installed, a request for discoverability examples for the software application; and providing, by the voice action system, the data defining the discoverability example to the user device in response to the request, wherein the user device is configured, based at least on the data defining the discoverability example, to provide a notification of the one or more of the trigger terms when a status of the software application satisfies the specified context. 